Vote Testers!

The Association for Software Testing board elections are happening shortly. Terms are two years long but staggered so that half of the board is up for re-election every year. I've just finished my first term and I've decided to stand again, for a few reasons.

First, and accuse me of whatever cheesiness you like here, I truly believe in the AST's ethical code and mission:

The Association for Software Testing is dedicated to advancing the understanding of the science and practice of software testing according to Context-Driven principles.

It's important to me that I remain a practitioner of testing, and I roll my expertise and experience into the context when I practice.

Second, and with another helping from the cheeseboard, the AST is emotionally significant to me. When I started testing it was the organisation that Lessons Learned in Software Testing led me to, and its Black Box Software Testing courses helped to culture and mould my intuitions about testing and how I wanted to test.

Third, and onto the coffee now for the business talk, I feel like I have unfinished work that I want to complete.

Next week there are hustings and the candidates have been asked to provide answers to a handful of questions. I thought I'd publish mine here as I did for a similar set after the 2019 elections.

Diversity

How do you intend to promote diversity within the AST? How could AST promote diversity, of all kinds, within our own organization and within the wider testing and technology
communities?

All AST members, including the board, sign up to a code of ethics which requires us to respect the diversity of cultures, not to discriminate on the basis of race, sex, religion, age, disability, national origin or other factors, and to consider whether the results of our work will be used in socially responsible ways.

When I answered the same question two years ago I said I would "encourage AST to seek out people who do not already engage with it and find ways to help them to engage. This might be by making AST relevant to them, by moving AST geographically closer to them, by making AST financially accessible to them, or something else."

I think I have been able to work towards that:

I argued in favour of setting explicit diversity goals, and we now have them for both the the board's composition and for the way we serve our members.
When I set up and ran a joint workshop with the British Computer Society's Special Interest Group on Software Testing on the societal impact of testing diversity of participants was a key requirement from the beginning of our planning.
I have recently been researching how the AST can make itself more accessible to those who are financially disadvantaged around the world. We're currently looking at Pay What You Can Afford models.

Black Box Software Testing

Please share your vision for the future of the AST's BBST program.

The recent move to partner with Altom for the provision of the Community Track of Black Box Software Testing is wonderful for multiple reasons. It brings back together the two major forks of BBST, it clears up the confusing relationship between them, and it provides shared resources for the teaching and maintenance of the materials.

On top of that, it preserves everything that's great about BBST: the depth, breadth, and quality of the material; the small cohort approach; and the dedicated and knowledgeable instructors. In the immediate future I'd like to see us continue to doing everything we can to help that to work well.

In the longer term there have been conversations around broadening the education offerings from the AST to include, for example, something on exploratory testing or automation. We recently ran a course in partnership with Rob Sabourin and I think more of those kinds of partnerships could work for us, because the cost of creating, running, and maintaining courses is high and we have limited resources.

History

What do you think the AST board has historically done well, and what do you think needs to change?

With only a small number of volunteer staff, I think the board has done extraordinarily well to keep the organisation running.

CAST, our conference, is a significant part of what AST is and is known for, and not having CAST in 2020 was a major setback for us. We redirected our CAST energy into more smaller events and we've put something on every month instead, experimenting with different formats like Fika, a super-short and sweet mini-CAST, and even next week's online hustings for the 2021 elections.

A significant challenge for AST has been that it can seem dry, dated, and distant, and the value of being a member can be unclear. In some respects we shoot ourselves in the foot because, while we are a member organisation, our mission is to promote testing in the world and we've tended to err towards making everything we have available to anyone who is interested.

However, despite that difficulty, I support the policy. I want the AST to make a difference to the world generally, to engage with people outside of our organisation, and to grow the testing craft everywhere.

Future of AST

If you are elected to serve on the board, what is your vision for the future of AST and what do you hope to accomplish as part of the board?

At the first AST board meeting I attended I presented a paper called Why Be A Member of the AST? In it, I compared the value we offered, how we communicated our value and where, and I started thinking about what our various activities cost us versus the value they brought to us and our membership.

Together we then worked on being explicit about what the AST stands for, what we think our members want from us, and what we want from our members.

Those activities naturally exposed places that we thought we could do better but it also helped us to prioritise activities to improve on them.

For the last two years I've been working through tasks from that list, incrementally improving what we do and how how we do it. To give some examples:

I revamped Become a Member to expose direct (e.g. learning, community), indirect (e.g. our reputation, our code of ethics), and general (e.g. promoting testing) value.
I researched our membership patterns and proposed a new structure and pricing to stabilise our member base and increase the value our members get. This saw the introduction of AST Champions and automatic life membership.
I wrote, organised, or contributed to three books for AST: Peers Exchanging Ideas, Navigating the World as a Context-Driven Tester, and Testing Stories.
I automated social media posts publicising our vast archive of testing resources.

The next major task for me is to make the cost of entry to AST more equitable.

For the AST more generally: I think there is a place in the world for a non-profit testing organisation advocating for high-quality, ethical, context-driven testing. We need to find better ways to help our tribe to find us, better ways to communicate what we stand for, why we think it is relevant and valuable, and why it's worth helping us to achieve it.

Conflicts of Interest

Please describe any current initiatives you participate in that might affect your ability to serve on the AST board, and serve the AST membership.

I don't have any.

Support

In what ways have you supported the mission of AST?

In lots of ways! I've mentioned some of the things I've done while on the board already. Here's a few examples of stuff I've done outside of AST that I think align with our mission:

I blog weekly (for the last ten years) from a context-driven perspective.
I am the organiser of the Cambridge Exploratory Workshop on Testing.
I speak about testing at work, in the local community, and at conferences.
I strive to demonstrate good work, done ethically, according to context-driven principles.
I invest time in helping others to test.
I invest time in helping myself to improve my testing.

Image: Wikipedia

Meet Me Halfway?

The Association for Software Testing is crowd-sourcing a book, Navigating the World as a Context-Driven Tester , which aims to provide responses to common questions and statements about testing from a context-driven perspective . It's being edited by Lee Hawkins who is posing questions on Twitter , LinkedIn , Mastodon , Slack , and the AST mailing list and then collating the replies, focusing on practice over theory. I've decided to contribute by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me? --00-- "Stop answering my questions with questions." Sure, I can do that. In return, please stop asking me questions so open to interpretation that any answ...

How do I Test AI?

Recently a few people have asked me how I test AI. I'm happy to share my experiences, but I frame the question more broadly, perhaps something like this: what kinds of things do I consider when testing systems with artificial intelligence components . I freestyled liberally the first time I answered but when the question came up again I thought I'd write a few bullets to help me remember key things. This post is the latest iteration of that list. Caveats: I'm not an expert; what you see below is a reminder of things to pick up on during conversations so it's quite minimal; it's also messy; it's absolutely not a guide or a set of best practices; each point should be applied in context; the categories are very rough; it's certainly not complete. Also note that I work with teams who really know what they're doing on the domain, tech, and medical safety fronts and some of the things listed here are things they'd typically do some or all of. Testing ...

The Best Programmer Dan Knows

I was pairing with my friend Vernon at work last week, on a tool I've been developing. He was smiling broadly as I talked him through what I'd done because we've been here before. The tool facilitates a task that's time-consuming, inefficient, error-prone, tiresome, and important to get right. Vern knows that those kinds of factors trigger me to change or build something, and that's why he was struggling not to laugh out loud. He held himself together and asked a bunch of sensible questions about the need, the desired outcome, and the approach I'd taken. Then he mentioned a talk by Daniel Terhorst-North, called The Best Programmer I Know, and said that much of it paralleled what he sees me doing. It was my turn to laugh then, because I am not a good programmer, and I thought he knew that already. What I do accept, though, is that I am focussed on the value that programs can give, and getting some of that value as early as possible. He sent me a link to the ta...

Notes on Testing Notes

Ben Dowen pinged me and others on Twitter last week , asking for "a nice concise resource to link to for a blog post - about taking good Testing notes." I didn't have one so I thought I'd write a few words on how I'm doing it at the moment for my work at Ada Health, alongside Ben. You may have read previously that I use a script to upload Markdown-based text files to Confluence . Here's the template that I start from: # Date + Title # Mission # Summary WIP! # Notes Then I fill out what I plan to do. The Mission can be as high or low level as I want it to be. Sometimes, if deeper context might be valuable I'll add a Background subsection to it. I don't fill in the Summary section until the end. It's a high-level overview of what I did, what I found, risks identified, value provided, and so on. Between the Mission and Summary I hope that a reader can see what I initially intended and what actually...

On Herding Cats

Last night I was at the Cambridge Tester meetup for a workshop on leadership. It was a two-parter with Drew Pontikis facilitating conversation about workplace scenarios followed by an AMA with a group of experienced managers. I can't come to work this week, my cat died. Drew opened by asking us what our first thoughts would be as managers on seeing that sentence. Naturally, sadness and sympathy, followed by a week ? for a cat ? and I only got a day for my gran! Then practicalities such as maybe there's company policy that covers that , and then the acknowledgement that it's contextual: perhaps this was a long-time emotional support animal . Having established that management decisions are a mixture of emotion, logic, and contingency Drew noted that most of us don't get training in management or leadership then split us into small groups and confronted us with three situations to talk through: Setting personal development goals for others. Dropping a clange...

Reasonable Doubt

In Your job is to deliver code you have proven to work Simon Willison writes: As software engineers we ... need to deliver code that works — and we need to include proof that it works as well. He is coming at this from the perspective of LLM-assisted coding, but most of what he says applies in general. I think this is a reasonable consise summary of his requirements for developers: Manual happy paths: get the system into an initial state, exercise the code, check that it has the desired effect on the state. Manual edge cases: no advice given, just a note that skill here is a sign of a senior engineer. Automated tests: should demonstrate the change like Manual happy paths but also fail if the change is reverted. He notes that, even though LLM tooling can write automated tests, it's humans who are accountable for the code and it's on us to "include evidence that it works as it should." Coincidentally, just the week before I read his post I told one of my...

Vanilla Flavour Testing

I have been pairing with a new developer colleague recently. In our last session he asked me "is this normal testing?" saying that he'd never seen anything like it anywhere else that he'd worked. We finished the task we were on and then chatted about his question for a few minutes. This is a short summary of what I said. I would describe myself as context-driven . I don't take the same approach to testing every time, except in a meta way. I try to understand the important questions, who they are important to, and what the constraints on the work are. With that knowledge I look for productive, pragmatic, ways to explore whatever we're looking at to uncover valuable information or find a way to move on. I write test notes as I work in a format that I have found to be useful to me, colleagues, and stakeholders. For me, the notes should clearly state the mission and give a tl;dr summary of the findings and I like them to be public while I'm working not just w...

Why Test, Test What, Then How?

There was a time when testing was all about the mnemonics . Well, we had no AI back then so thinking about our human craft and how to share what we had learned using our human intelligence with other engaged humans for later recall in their human heads seemed important. But this post isn't about dumping on AI. It isn't about mnemonics either even if WTTWTH does look like something that'd fit well into that ancient world. No, this post is just a snappier version of what I said to my team this week when I was walking through some testing I'd done the day before. It was concerned with a change to a particular turn in the dialog system we're building where multiple variables are in play, some populated by an external call to an LLM service. I wanted to make the point that the bulk of the testing work was done in the research I did and the spreadsheet I made, not in the interaction with our product. That spreadsheet was the result of me looking in our service's cod...

Open Your Mind

Jerome Groopman, in How Doctors Think , reviews ways in which doctors can make poor choices, identifies potential causes, and suggests some practices, for both doctor and patient, that can help to prevent them. I find this interesting for a couple of reasons: first, I work in the health space, although not in a therapeutic area and, second, I like to reflect on my own thought processes. I'll take three broad themes from Groopman's analysis: the business of healthcare and how that impacts a physician's ability to practice; the doctor-patient relationship and how that impacts the experience of both sides; and the cognitive failings that impact a correct and timely diagnosis for any given patient. Naturally, these overlap. The book is written from the perspective of the notoriously commercialised American medical system and is around 20 years old, so doubtless some of the details are different outside of the US and have changed since pu...

Better Isolate Than Never

How do you test a product with distributed logic and non-deterministic components? Well, it depends on the product and when the question is asked. This post is one answer, for now. A service I work on exposes an API for internal and external clients and calls multiple other services. It orchestrates a reasonably complex journey for a user, with their inputs and the responses of the services determining each step. Our customers can configure the service to provide a variant of the standard journey for their users. This gives them choices on the available steps, the order of the steps, and, importantly, some of the logic for taking particular steps. This configuration lives in a different repository to the service, not owned by us, and it can be changed and deployed independently from the service. As you can imagine, we test our service in multiple ways at different granularities using the usual tooling, including unit tests fo...

Hiccupps

Search This Blog